-
Notifications
You must be signed in to change notification settings - Fork 159
Consolidate sdk documentation with tabs #2355
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Consolidate sdk documentation with tabs #2355
Conversation
Co-authored-by: jannik <[email protected]>
|
Cursor Agent can help with this pull request. Just |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📦 Next.js Bundle Analysis for langfuse-docsThis analysis was generated by the Next.js Bundle Analysis action. 🤖 New Pages AddedThe following pages were added to the bundle from the code in this PR:
One Page Changed SizeThe following page changed size from the code in this PR compared to its base branch:
DetailsOnly the gzipped size is provided here based on an expert tip. First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If Any third party scripts you have added directly to your app using the The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored. |
Co-authored-by: jannik <[email protected]>
Unify Python and JS/TS SDK documentation into a single section using tabs to improve discoverability and reduce redundancy.
The previous documentation had separate sections for Python and JS/TS SDKs, despite having largely similar features. This PR merges these into a single, cohesive SDK section, where each feature page uses
<Tabs>to present language-specific examples. This streamlines the user experience by centralizing SDK information and making it easier to compare implementations across languages. It also involves updating all internal links and redirects to point to the new structure.